Repository navigation
Keep CONFORMANCE.md the requirement table the Part 4 rows are held to - #92
Merged
Merged
Conversation
CONFORMANCE.md keyed each requirement of the class cquery to its code and test, and also stated the aggregations, the lifecycle, the delivery and the extensions. What the service answers is stated by the MobilityDB specification doc/specs/mobilityapi-ogc-api.md, so the file keeps the table ats_part4_test.go reads and points to the specification for the rest.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CONFORMANCE.mdis the tableats_part4_test.goreads: each requirement of the classcquery, keyed by the draft's number and identifier, with the code that meets it and the test that reads it. What the service declares and answers is stated by the MobilityDB specificationdoc/specs/mobilityapi-ogc-api.md(MobilityDB/MobilityDB#3836), which carries the aggregations, the lifecycle, the delivery, live ingestion, the streaming engines and the extensions, so the file keeps the table and points to the specification.The comment on the geometry position stream in
routeTablestates that no requirement of Part 4 covers it.The table is the one
TestATSPart4RowsAreTheRecordedRequirementsreads, row for row.